NetworkWatcher: Added new parameters to QueryConnectionMonitorResult and ConnectivityCheckRequest#2763
NetworkWatcher: Added new parameters to QueryConnectionMonitorResult and ConnectivityCheckRequest#2763olydis merged 8 commits intoAzure:masterfrom irrogozh:master
Conversation
…and ConnectivityCheckRequest
Automation for azure-libraries-for-javaThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
Automation for azure-sdk-for-nodeA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
|
Hi @irrogozh @MikhailTryakhov we neel to Ack on CHanges for Networking that are against master, please follow up with him =Thanks, Samer |
| "ProtocolConfiguration": { | ||
| "description": "Configuration of the protocol.", | ||
| "properties": { | ||
| "hTTPConfiguration": { |
There was a problem hiding this comment.
is hTTP case expected?
|
LGTM |
| ], | ||
| "x-ms-enum": { | ||
| "name": "Protocol", | ||
| "name": "IpFlowProtocol", |
| }, | ||
| "ConnectionMonitorQueryResult": { | ||
| "properties": { | ||
| "sourceStatus": { |
There was a problem hiding this comment.
breaking change 2 (constructor signature)
|
@MikhailTryakhov @salameer FYI, there are SDK breaking changes (see my comments) but indeed no API breakage. |
|
@olydis I meant no API breakage. I needed Anu because have no rights to approve :) now it can be merged |
|
@MikhailTryakhov well, all reviewers (like me) have the power to merge, so whoever is assigned to a PR will be the POC 🙂 |
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger